refactor(repo): Move typedoc reflection work into custom-theme, reduce extract-methods#9073
refactor(repo): Move typedoc reflection work into custom-theme, reduce extract-methods#9073alexisintech wants to merge 14 commits into
Conversation
…e extract-methods to a marker slicer Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: 0ab4672 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Repository UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (2)
📝 WalkthroughWalkthroughThis PR updates the TypeDoc pipeline to slice rendered markdown into extracted method pages, adds ChangesTypeDoc pipeline rework
Documentation comment updates
Estimated code review effort: 4 (Complex) | ~45 minutes Possibly related PRs
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
Comment |
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/electron
@clerk/electron-passkeys
@clerk/eslint-plugin
@clerk/expo
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
… sub-docs Extend custom-theme.mjs so every reference-object and backend-api parent page carries all method info in a canonical `## `name()`` / `## `name`` H2 shape: - renderAggregatorMethodSection synthesizes sections for callable members typedoc doesn't emit naturally (function-typed interface properties, extraMethodInterfaces, @extractMethods namespace callables emitted with qualified names). - insertSignatureBlocksIntoNaturalMethodSections injects a ```typescript block after each backend-class method's description so natural and synthesized sections share one shape. - removeMethodH2Section strips typedoc's per-overload `### Call Signature` sub-headings and lets the aggregator re-emit a single section for the primary signature. - renderAggregatorPropertyTableSection emits `## `name`` H2s for @extractMethods namespaces (listing non-callable members) and their non-callable object-shape members (expanding the object shape). Reduce extract-methods.mjs to a pure text-slicer over those sections. Zero reflection access downstream. findMethodH2Sections detects both `## `name()`` and `## `name`` shapes; reshape helpers demote to H3 and reflow into the per-method / per-property-table sub-doc shape (byte-identical to what the previous marker-block builders produced). Delete the marker-block emission entirely: renderInlineMethodsBlock, buildMethodMdx, extractCallableMembersFromDeclaration, processExtractMethodsNamespace, buildPropertyTableDocMdx, buildExtractMethodsNamespacePropertyTableMdx, and orphaned appendSignatureOnlyReturns removed from custom-theme.mjs; parseMethodMarkers, stripMethodsBlock, and both marker-block fallback paths removed from extract-methods.mjs. The `<!-- clerk:properties-start/end -->` markers stay — properties.mdx extraction still uses them post-prettier for column alignment. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
alexisintech
changed the title
…ctural guards
Audit-driven cleanups of `.typedoc/custom-theme.mjs` (3622 → 3464 lines). Every
edit was regenerated and `diff -rq`-verified against the pre-refactor baseline —
byte-identical output.
- Extract `wrapInlineTypeAsCode()`. Replaces the strip-backticks / strip-code-tags /
conditional single-wrap block that was copy-pasted across `declarationType`,
`unionType`, `functionType`, `arrayType`, and `reflectionType`. `functionType`'s
split-map-join around the delimiter was decorative — global `String.replace`
produces identical output on the whole string.
- Delete duplicate-typedoc structural guards. `isIntersectionTypeDoc` /
`isReferenceTypeDoc` / `isReflectionTypeDoc` / `isUnionTypeDoc` /
`coerceUnionTypeIfNeeded` existed to work around `instanceof` failing when
multiple TypeDoc copies were loaded into the tree. `find node_modules -name
typedoc` confirms a single copy under the current pnpm layout, so plain
`instanceof` works reliably. Simplifies `someType`, `declaration`,
`collectPropertyReflectionsFromIntersectionArm`, and
`isArrayElementReferenceInliningToUnion`.
- Simplify OAuth-strategy collapse helpers. Drop the `typeof
project.getReflectionsByKind === 'function'` runtime guard (stable in TypeDoc
0.28) and the useless `findNamedTypeDeclaration` fallback in
`findOAuthStrategyDeclaration` (both real `OAuthStrategy` declarations —
`packages/shared` and `packages/backend` — are TypeAliases). Inline the
`sourcePath` local. Convert `flattenUnionTypeMembersForOAuthCollapse` to
`instanceof UnionType`. The collapse itself stays — TypeScript flattens
`` `oauth_${OAuthProvider}` `` eagerly, so there is no `ReferenceType` for the
theme to preserve.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ents Bulk of the ~45 `pattern`/`replace` entries in `getCatchAllReplacements()` were the same shape: bare identifier not already inside a link/code/anchor → `[Name](/docs/…)`. Move those into a `CATCH_ALL_TYPE_LINKS` data table of `[name, url]` (or `[name, url, linkText]` when the display name differs from the match, as with `LoadedClerk` → `Clerk`), derive the regex from the name via a small `catchAllBareSymbolRegex` helper, and keep the five genuine one-offs inline (`SessionResource[]` array-suffix regex, `Appearance<Theme>`, `(CreateOrganizationParams)` in-page anchor, `**Deprecated**` full-stop, and the `**Default**` / `**Example**` / `**Examples**` prose rewrites). Also splits the previous `(SignIn|SignUp)Errors` regex into two data-table entries so every link rule is a simple identifier + url pair — makes adds trivial. `custom-plugin.mjs`: 692 → 572 lines. Byte-identical output vs baseline. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…er tag
Types that clerk-docs embeds via `<Typedoc />` inside hand-written pages need
typedoc-plugin-markdown's `## Properties` group heading suppressed so the
embedded fragment doesn't collide with the parent page's heading hierarchy.
Previously this was a hardcoded array of 33 filenames + a post-hoc regex strip
in `custom-plugin.mjs` — long-standing TODO to move the trigger to the source
declaration.
- New `@noHeading` modifier tag registered in `typedoc.config.mjs` (both
`modifierTags` and `notRenderedTags`; also added to the theme's hidden-tag
set in the `comment` partial so it doesn't render as a `**No Heading**`
badge — typedoc-plugin-markdown ignores `notRenderedTags` for modifier tags).
- `custom-theme.mjs` `MarkdownPageEvent.END` listener strips the first heading
(any level H1-H6) via `output.contents.replace(/^#{1,6} .+\n+/m, '')` when
`decl.comment.hasModifier('@noHeading')`.
- Added `/** @noHeading */` to the 31 source declarations that emit today's
live entries (verified by empty-array-then-diff experiment; 3 filenames in
the original list were dead — no typedoc-emitted file matched them). Also
added `@noHeading` to `PaginatedHookConfig` because typedoc's comment
inheritance for `interface HookParams extends PaginatedHookConfig<…>`
replaces `HookParams`'s modifier tags with the parent's — tagging the
parent gets it inherited (parent is `@inline` so it has no page of its own).
- Deleted `FILES_WITHOUT_HEADINGS` and its strip from `custom-plugin.mjs`.
`custom-plugin.mjs`: 573 → 514 lines. Byte-identical output vs baseline.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The `accessor` partial in `ClerkMarkdownThemeContext` is never invoked.
typedoc-plugin-markdown would dispatch to `partials.accessor` from its default
`member` partial for accessor-kind reflections, but the theme's custom `member`
partial returns `''` for accessors and short-circuits that path — accessor
rendering happens in `memberWithGroups` (as a compact "Property" table)
instead. The header comment already hedged this ("Fallback single-row
rendering if used directly elsewhere"); nothing does.
Verified byte-identical output vs baseline.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The `swap()` function was a three-line array-index swap used exactly once by the `signature` partial to reorder the `@displayFunctionSignature` output. Inline as destructuring so the transformation is legible without a jump-away. Verified byte-identical output vs baseline. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
`grep -rln "@paramExtension" packages/*/src` returns zero hits — the tag is never used on any source declaration. The custom handler in the `signature` partial (which would insert extra content after the Parameters section) was therefore unreachable. Removes the handler branch plus the tag registration in `CUSTOM_BLOCK_TAGS`. The `@displayFunctionSignature` swap logic that shared the same split/join scaffolding is simplified to a direct return path. Verified byte-identical output vs baseline. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…uplicating `escapeChars` was defined twice — once in `.typedoc/markdown-helpers.mjs` (exported) and once as a local function in `.typedoc/custom-theme.mjs`, with byte-identical bodies. Import the shared version and delete the local copy. Verified byte-identical output vs baseline. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
alexisintech
force-pushed
the
aa/docs-11892
branch
from
3715853 to
068c809
Compare
alexisintech
changed the title
alexisintech
changed the title
Merged `main` into `aa/docs-11892` (see prior merge commit). Two of the three regenerated snapshots are cosmetic-only — column-width padding shifted after merged source updates changed the widest row in each table. The third (`clerk.mdx`) also captures two new fields on `ClerkAuthenticateWithWeb3Params` (`protectCheckUrl?`, `signUpProtectCheckUrl?`) added on main. All 16 `.typedoc/__tests__/` tests pass locally when run from `.typedoc/`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
alexisintech
changed the title
API Changes Report
Summary
@clerk/sharedCurrent version: 4.25.0 Subpath
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (1)
.typedoc/extract-methods.mjs (1)
216-216: 🚀 Performance & Scalability | 🔵 Trivial | 💤 Low valueMinor: simplify the trailing-separator trim regex.
/^(\s|\*+\s*)*$/uses nested quantifiers over overlapping alternatives (both branches can match whitespace), a shape prone to backtracking. Input here is short trailing lines so it's not a practical risk, but an equivalent, backtracking-free form is clearer:♻️ Optional simplification
- while (sectionLines.length && /^(\s|\*+\s*)*$/.test(sectionLines[sectionLines.length - 1])) sectionLines.pop(); + while (sectionLines.length && /^[\s*]*$/.test(sectionLines[sectionLines.length - 1])) sectionLines.pop();🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.typedoc/extract-methods.mjs at line 216, The trailing-separator trim check in extract-methods.mjs uses an overly complex regex with overlapping whitespace branches, so simplify the condition in the sectionLines pop loop to an equivalent, clearer pattern that matches blank or asterisk-prefixed separator lines without nested backtracking. Update the regex used in the while statement in the section trimming logic only, keeping the same behavior while making the intent easier to read and maintain.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@packages/shared/src/react/hooks/usePaymentAttemptQuery.types.ts`:
- Around line 17-25: The JSDoc for PaymentAttemptQueryResult.error is out of
sync with the exported type, since the property is ClerkAPIResponseError | null
rather than undefined. Update the comment in usePaymentAttemptQuery.types so the
error description matches the actual union type and states null is the empty
value; keep the rest of PaymentAttemptQueryResult aligned with the documented
loading and data fields.
In `@packages/shared/src/react/hooks/usePlanDetailsQuery.types.ts`:
- Around line 16-24: The JSDoc on PlanDetailsQueryResult.error is inconsistent
with its type, since the property is ClerkAPIResponseError | null but the
comment says undefined. Update the error documentation in
usePlanDetailsQuery.types so it matches the actual union and reflects null as
the no-error state, keeping the wording aligned with the other fields in
PlanDetailsQueryResult.
In `@packages/shared/src/react/hooks/useStatementQuery.types.ts`:
- Around line 17-25: The JSDoc for the `error` field in
`useStatementQuery.types` is out of sync with the hook behavior. Update the
comment in `UseStatementQueryResult` so it documents `null` as the no-error
value, matching `useStatementQuery.tsx` and its `query.error ?? null` return,
and keep the rest of the type definition unchanged.
In `@packages/shared/src/types/signInFuture.ts`:
- Around line 16-17: The `strategy` field in `SignInFuture` is described too
narrowly as a “first factor verification strategy,” which can misrepresent the
exported API for the `OAuthStrategy`, `enterprise_sso`, `PasskeyStrategy`, and
`TicketStrategy` union. Update the JSDoc on `strategy` in `SignInFuture` to use
a neutral “authentication strategy” description that still explains it depends
on `identifier` and that supported strategies vary by authentication identifier.
---
Nitpick comments:
In @.typedoc/extract-methods.mjs:
- Line 216: The trailing-separator trim check in extract-methods.mjs uses an
overly complex regex with overlapping whitespace branches, so simplify the
condition in the sectionLines pop loop to an equivalent, clearer pattern that
matches blank or asterisk-prefixed separator lines without nested backtracking.
Update the regex used in the while statement in the section trimming logic only,
keeping the same behavior while making the intent easier to read and maintain.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Repository UI (inherited)
Review profile: CHILL
Plan: Pro Plus
Run ID: d84060d4-3f13-4703-9c52-3f524306f892
📒 Files selected for processing (52)
.changeset/typedoc-marker-slicer.md.typedoc/__tests__/__snapshots__/api-key-resource-methods-create.mdx.typedoc/__tests__/__snapshots__/clerk-properties.mdx.typedoc/__tests__/__snapshots__/clerk.mdx.typedoc/__tests__/__snapshots__/user-resource-properties.mdx.typedoc/custom-plugin.mjs.typedoc/custom-theme.mjs.typedoc/extract-methods.mjs.typedoc/extract-returns-and-params.mjspackages/backend/src/api/endpoints/BillingApi.tspackages/backend/src/api/endpoints/EnterpriseConnectionApi.tspackages/backend/src/api/endpoints/OrganizationApi.tspackages/backend/src/api/endpoints/UserApi.tspackages/backend/src/api/resources/OrganizationMembership.tspackages/backend/src/tokens/types.tspackages/backend/src/tokens/verify.tspackages/backend/src/webhooks.tspackages/expo/src/local-credentials/useLocalCredentials/useLocalCredentials.tspackages/nextjs/src/server/createGetAuth.tspackages/react/src/hooks/useAuth.tspackages/shared/src/react/billing/payment-element.tsxpackages/shared/src/react/contexts.tsxpackages/shared/src/react/hooks/createBillingPaginatedHook.tsxpackages/shared/src/react/hooks/useAPIKeys.tsxpackages/shared/src/react/hooks/useOAuthConsent.types.tspackages/shared/src/react/hooks/useOrganization.tsxpackages/shared/src/react/hooks/useOrganizationCreationDefaults.types.tspackages/shared/src/react/hooks/useOrganizationList.tsxpackages/shared/src/react/hooks/usePaymentAttemptQuery.types.tspackages/shared/src/react/hooks/usePaymentAttempts.tsxpackages/shared/src/react/hooks/usePaymentMethods.tsxpackages/shared/src/react/hooks/usePlanDetailsQuery.types.tspackages/shared/src/react/hooks/usePlans.tsxpackages/shared/src/react/hooks/useReverification.tspackages/shared/src/react/hooks/useStatementQuery.types.tspackages/shared/src/react/hooks/useStatements.tsxpackages/shared/src/react/hooks/useSubscription.types.tspackages/shared/src/react/types.tspackages/shared/src/types/apiKeys.tspackages/shared/src/types/billing.tspackages/shared/src/types/clerk.tspackages/shared/src/types/client.tspackages/shared/src/types/factors.tspackages/shared/src/types/hooks.tspackages/shared/src/types/multiDomain.tspackages/shared/src/types/organizationDomain.tspackages/shared/src/types/session.tspackages/shared/src/types/signInFuture.tspackages/shared/src/types/signUpFuture.tspackages/shared/src/types/telemetry.tspackages/shared/src/types/user.tstypedoc.config.mjs
| /** The first factor verification strategy to use in the sign-in flow. Depends on the `identifier` value. Each authentication identifier supports different verification strategies. */ | ||
| strategy?: OAuthStrategy | 'enterprise_sso' | PasskeyStrategy | TicketStrategy; |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Broaden the strategy description.
PasskeyStrategy and TicketStrategy are part of this union, so “first factor verification strategy” is too narrow for the exported API and can mislead generated docs. Consider a neutral “authentication strategy” description instead.
♻️ Proposed fix
- /** The first factor verification strategy to use in the sign-in flow. Depends on the `identifier` value. Each authentication identifier supports different verification strategies. */
+ /** The authentication strategy to use in the sign-in flow. */📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| /** The first factor verification strategy to use in the sign-in flow. Depends on the `identifier` value. Each authentication identifier supports different verification strategies. */ | |
| strategy?: OAuthStrategy | 'enterprise_sso' | PasskeyStrategy | TicketStrategy; | |
| /** The authentication strategy to use in the sign-in flow. */ |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/shared/src/types/signInFuture.ts` around lines 16 - 17, The
`strategy` field in `SignInFuture` is described too narrowly as a “first factor
verification strategy,” which can misrepresent the exported API for the
`OAuthStrategy`, `enterprise_sso`, `PasskeyStrategy`, and `TicketStrategy`
union. Update the JSDoc on `strategy` in `SignInFuture` to use a neutral
“authentication strategy” description that still explains it depends on
`identifier` and that supported strategies vary by authentication identifier.
1 participant
Description
Unifies the
.typedoc/pipeline so every reference-object and backend-api parent page carries all the info its extracted sub-docs need in a canonical##H2 shape, andextract-methods.mjsbecomes a pure text-slicer over those H2s — no reflection access, no marker block. Same generated docs.Before:
extract-methods.mjswas a second reflection walker layered on top of the markdown theme. It re-imported TypeDoc AST types, re-derived method/property partitioning, and re-invokedMarkdownThemeContextpartials to build each per-method MDX file. Two places in the codebase had to agree on how methods vs properties are partitioned, which acronyms slug how, and which comment tags trigger inline extraction.After: all reflection work lives in
custom-theme.mjs, which now synthesizes:## `name()`H2 sections for every callable member that typedoc-plugin-markdown doesn't emit naturally (function-typed interface properties,
extraMethodInterfaces,@extractMethodsnamespace callables likeemailCode.sendCode). Backend-class methods get a```typescriptsignature block injected after their natural description so all H2s share one shape.## `name`H2 sections for
@extractMethodsnamespaces with non-callable object-shape members (emailLinkonSignInFutureResource) and each such non-callable member (emailLink.verification) — the same rows the marker-block builders used to write directly to sub-docs.Overloaded backend-class methods: strip typedoc's per-overload
### Call Signaturesub-headings and re-emit a single section for the primary signature, so the parent's shape is uniform across single- and multi-overload methods.extract-methods.mjsslices those H2s pre-prettier, reshapes each intomethods/<slug>.mdx(H2 → H3, then straight verbatim), and defers Properties extraction to apreWriteAsyncJobthat reads the (now prettier-aligned)<!-- clerk:properties-start/end -->markers and writesproperties.mdx.Commits
refactor(repo): move typedoc reflection work into custom-theme, reduce extract-methods to a marker slicer— the first move: reflection walks live in one place,extract-methodsreads marker-wrapped output produced by the theme. Byte-identical to the pre-refactor docs.refactor(repo): text-slice parent H2 aggregator sections into methods sub-docs— the follow-through: parent pages carry the info directly (methods + property tables),extract-methodsbecomes a pure text-slicer, and the marker-block emission is deleted entirely. Byte-identical for every sub-doc; the only expected output delta is the parent pages themselves, which now show their##name()/ `## `nameH2 sections in full.refactor(repo): consolidate custom-theme code-wrap and drop dead structural guards— audit follow-up oncustom-theme.mjs: extract onewrapInlineTypeAsCodehelper across the 5 partials that used to open-code the strip-backticks / single-wrap dance; delete the four structural type-check helpers pluscoerceUnionTypeIfNeededafter confirming a singletypedoccopy under pnpm makesinstanceofreliable; simplify the OAuth-strategy collapse helpers. 3622 → 3464 lines. Byte-identical output.refactor(repo): data-drive custom-plugin catch-all type-link replacements— the ~45pattern/replaceentries ingetCatchAllReplacements()collapse into aCATCH_ALL_TYPE_LINKSdata table of[name, url](plus a third field for the rare cases where the display name differs from the match, e.g.LoadedClerk→Clerk), with the regex derived fromname. Five genuine one-offs stay inline (SessionResource[]array-suffix regex,Appearance<Theme>,(CreateOrganizationParams)in-page anchor,**Deprecated**full-stop, and the**Default**/**Example**/**Examples**prose rewrites). Adding a new type link is now one row. 692 → 572 lines. Byte-identical output.refactor(repo): replace FILES_WITHOUT_HEADINGS with @noHeading modifier tag— the long-standing TODO on.typedoc/custom-plugin.mjs's 33-filename allowlist finally lands. Types embedded via<Typedoc />inside hand-written docs now opt into heading suppression at the source with/** @noHeading */; the theme'sMarkdownPageEvent.ENDlistener strips the first heading (any level H1-H6) viaoutput.contents.replace(/^#{1,6} .+\n+/m, '')when the reflection carries the modifier. 31 declarations tagged (verified by empty-array-then-diff experiment — 3 filenames in the original list were dead). Also taggedPaginatedHookConfigbecause typedoc's comment inheritance forinterface HookParams extends PaginatedHookConfig<…>clobbers the child's modifier tags with the parent's — the parent is@inlineso it doesn't emit its own page. Byte-identical output.refactor(repo): remove dead accessor partial from custom-theme— theaccessorpartial inClerkMarkdownThemeContextwas never invoked: typedoc-plugin-markdown would dispatch to it from its defaultmemberpartial for accessor-kind reflections, but the theme's custommemberreturns''for accessors and short-circuits that path (accessors render as a compact "Property" table inmemberWithGroupsinstead). −11 lines, byte-identical output.refactor(repo): inline swap() helper into signature partial— three-line array-index swap used exactly once by thesignaturepartial to reorder@displayFunctionSignatureoutput. Inlined as destructuring so the transformation is legible without a jump-away. −15 lines net, byte-identical output.refactor(repo): remove dead @paramExtension handler and tag registration—grep -rln "@paramExtension" packages/*/srcreturned zero hits; the tag was registered inCUSTOM_BLOCK_TAGSbut never used on any source declaration, making the ~25-line handler branch in thesignaturepartial unreachable. Removed the handler, dropped the tag fromCUSTOM_BLOCK_TAGS, and simplified the sibling@displayFunctionSignaturepath that shared the same split/join scaffolding. −32 lines net, byte-identical output.refactor(repo): import escapeChars from markdown-helpers instead of duplicating—escapeCharswas defined twice with byte-identical bodies (once exported from.typedoc/markdown-helpers.mjs, once as a local in.typedoc/custom-theme.mjs). Import the shared version. −17 lines net, byte-identical output.Refs
Checklist
pnpm testruns as expected. (.typedocvitest: 16/16 pass)pnpm buildruns as expected.Type of change
Summary by CodeRabbit
New Features
isFetchingflag toStatementQueryResult.Documentation
Tests